Capacity management of an asynchronous transfer mode interface in a wireless communication infrastructure

ABSTRACT

Methods and apparatus that effectively manage capacity of a wireless-based communication infrastructure are presented herein. An evaluation component can generate configuration data associated with a base station of a cellular wireless network. Further, a radio network controller component can determine capacity of a physical port coupled between a radio network controller and the base station. The radio network controller component can configure the radio network controller to utilize an increase in capacity of the physical port based on the determined capacity of the physical port. A base station component can configure the base station to utilize the increase in capacity of the physical port based on the configuration data generated by the evaluation component.

CROSS-REFERENCE TO RELATED APPLICATION

This patent application is a continuation of U.S. patent applicationSer. No. 12/576,059 filed Oct. 8, 2009, and entitled “CAPACITYMANAGEMENT OF AN ASYNCHRONOUS TRANSFER MODE INTERFACE IN A WIRELESSCOMMUNICATION INFRASTRUCTURE,” the entirety of which is incorporated byreference herein.

TECHNICAL FIELD

This disclosure relates generally to capacity management of anasynchronous transfer mode interface in a wireless communicationinfrastructure.

BACKGROUND

Increased capability of various wireless communication devices, e.g.,smartphones connected to the internet, can burden available bandwidthbetween a local wireless communications cite, e.g., cellular basestation, and an associated core network. For example, bandwidthconstraints of a wired infrastructure between the cellular base stationand core network can degrade the performance of affected smartphoneswhen multiple smartphone customers demand bandwidth intensiveinformation at the same time.

To improve wireless customer experiences, wireless providers canincrease the bandwidth of the wired infrastructure by addingcommunications pipes, e.g., T1 lines, fiber optic cable, etc., betweenthe base station and core network. For example, each additional T1 linecan increase the bandwidth of the wired infrastructure by approximately1.5 Megabits/second. Utilizing this increased bandwidth, however, can becumbersome and costly due to manual programming of components within anassociated network. Moreover, because technology can be distinct betweenbase stations, such programming can be error prone, inconsistent, andtime-consuming

The above-described deficiencies of today's wireless communicationnetworks and related technologies are merely intended to provide anoverview of some of the problems of conventional systems, and are notintended to be exhaustive. Other problems with the state of the art, andcorresponding benefits of some of the various non-limiting embodimentsdescribed herein, may become further apparent upon review of thefollowing detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the subject disclosureare described with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 illustrates a wireless environment that includes macro cells andbase stations for wireless coverage, in accordance with an embodiment.

FIG. 2 illustrates a demonstrative system for effectively managingcapacity of a wireless-based communication infrastructure, in accordancewith an embodiment.

FIG. 3 illustrates a capacity management component for effectivelymanaging capacity of a wireless-based communication infrastructure, inaccordance with an embodiment.

FIG. 4 illustrates an evaluation component, in accordance with anembodiment.

FIG. 5 illustrates another evaluation component, in accordance with anembodiment.

FIG. 6. illustrates yet another evaluation component, in accordance withan embodiment.

FIG. 7 illustrates a radio network controller (RNC) component, inaccordance with an embodiment.

FIG. 8 illustrates another RNC component, in accordance with anembodiment.

FIG. 9 illustrates an RNC component that includes a correlationcomponent, in accordance with an embodiment.

FIG. 10 illustrates an RNC component that includes an asynchronoustransfer mode adaptation layer component, in accordance with anembodiment.

FIG. 11 illustrates an RNC component that includes an RNC scriptingcomponent 1010, in accordance with an embodiment.

FIG. 12 illustrates a base station component, in accordance with anembodiment.

FIG. 13 illustrates another demonstrative system 1200 for effectivelymanaging capacity of a wireless-based communication infrastructure, inaccordance with an embodiment.

FIG. 14 illustrates a process for effectively managing capacity of awireless-based communication infrastructure, in accordance with anembodiment.

FIG. 15 illustrates a process for assembling configuration informationassociated with one or more base stations of a cellular wirelessnetwork, in accordance with an embodiment.

FIG. 16 illustrates a process for configuring a radio networkcontroller, in accordance with an embodiment.

FIG. 17 illustrates a process for modifying an inverse multiplexing forasynchronous transfer mode group, in accordance with an embodiment.

FIG. 18 illustrates a process for configuring a base station, inaccordance with an embodiment.

FIG. 19 illustrates yet another process for effectively managingcapacity of a wireless-based communication infrastructure, in accordancewith an embodiment.

FIG. 20 illustrates a process for configuring at least one base stationand a radio network controller in a Universal Mobile TelecommunicationSystem, in accordance with an embodiment.

FIG. 21 illustrates a process for automatically creating configurationinformation, in accordance with an embodiment.

FIG. 22 illustrates a process for automatically determining whether aphysical interface includes unused bandwidth, in accordance with anembodiment.

FIG. 23 illustrates a process for automatically configuring a cellularwireless network to utilize unused bandwidth, in accordance with anembodiment.

FIG. 24 illustrates a block diagram of a base station, in accordancewith an embodiment.

FIG. 25 illustrates a block diagram of a wireless network environment,in accordance with an embodiment.

FIG. 26 illustrates a block diagram of a computer operable to executethe disclosed methods and apparatus, in accordance with an embodiment.

FIG. 27 illustrates a schematic block diagram of an exemplary computingenvironment, in accordance with an embodiment.

DETAILED DESCRIPTION

Various non-limiting embodiments of methods and apparatus are providedfor managing capacity in an asynchronous transfer mode interface withina wireless communication infrastructure.

In the following description, numerous specific details are set forth toprovide a thorough understanding of the embodiments. One skilled in therelevant art will recognize, however, that the techniques describedherein can be practiced without one or more of the specific details, orwith other methods, components, materials, etc. In other instances,well-known structures, materials, or operations are not shown ordescribed in detail to avoid obscuring certain aspects.

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearances of the phrase “in oneembodiment” or “in an embodiment” in various places throughout thisspecification are not necessarily all referring to the same embodiment.Furthermore, the particular features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments.

As utilized herein, terms “component,” “system,” “platform,” “node,”“layer,” “selector,” “interface,” and the like are intended to refer toa computer-related entity, hardware, software (e.g., in execution),and/or firmware. For example, a component can be a process running on aprocessor, a processor, an object, an executable, a program, a storagedevice, and/or a computer. By way of illustration, an applicationrunning on a server and the server can be a component. One or morecomponents can reside within a process and a component can be localizedon one computer and/or distributed between two or more computers.

Further, these components can execute from various computer readablemedia having various data structures stored thereon. The components maycommunicate via local and/or remote processes such as in accordance witha signal having one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network such as the Internet with other systemsvia the signal). As another example, a component can be an apparatuswith specific functionality provided by mechanical parts operated byelectric or electronic circuitry which is operated by a softwareapplication or a firmware application executed by a processor, whereinthe processor can be internal or external to the apparatus and executesat least a part of the software or firmware application. As yet anotherexample, a component can be an apparatus that provides specificfunctionality through electronic components without mechanical parts,the electronic components can include a processor therein to executesoftware or firmware that confers at least in part the functionality ofthe electronic components.

The word “exemplary” and/or “demonstrative” is used herein to meanserving as an example, instance, or illustration. For the avoidance ofdoubt, the subject matter disclosed herein is not limited by suchexamples. In addition, any aspect or design described herein as“exemplary” and/or “demonstrative” is not necessarily to be construed aspreferred or advantageous over other aspects or designs, nor is it meantto preclude equivalent exemplary structures and techniques known tothose of ordinary skill in the art. Furthermore, to the extent that theterms “includes,” “has,” “contains,” and other similar words are used ineither the detailed description or the claims, such terms are intendedto be inclusive—in a manner similar to the term “comprising” as an opentransition word—without precluding any additional or other elements.

Artificial intelligence based systems, e.g., utilizing explicitly and/orimplicitly trained classifiers, can be employed in connection withperforming inference and/or probabilistic determinations and/orstatistical-based determinations as in accordance with one or moreaspects of the disclosed subject matter as described herein. Forexample, an artificial intelligence system can be used, via evaluationcomponent 310 (described below), to automatically generate configurationdata associated with a base station of cellular wireless network. Inanother example, the artificial intelligence system can be used, viaradio controller component 320 (described below), to automaticallydetermine capacity of a physical port coupled between a radio networkcontroller (RNC) and the base station; and to configure the RNC toutilize an increase in capacity of the physical port based on thedetermined capacity of the physical port. In yet another example, theartificial intelligence system can automatically configure the basestation to utilize the increase in capacity of the physical port viabase station component 330 (described below). Moreover, the artificialintelligence system can be utilized under processes 2100, 2200, and2300, to automatically: create configuration information; determinewhether a physical interface includes unused bandwidth; and configure acellular wireless network to utilize the unused bandwidth, respectively.

As used herein, the term “infer” or “inference” refers generally to theprocess of reasoning about or inferring states of the system,environment, user, and/or intent from a set of observations as capturedvia events and/or data. Captured data and events can include user data,device data, environment data, data from sensors, sensor data,application data, implicit data, explicit data, etc. Inference can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events, for example. Inference can also referto techniques employed for composing higher-level events from a set ofevents and/or data. Such inference results in the construction of newevents or actions from a set of observed events and/or stored eventdata, whether the events are correlated in close temporal proximity, andwhether the events and data come from one or several event and datasources. Various classification schemes and/or systems (e.g., supportvector machines, neural networks, expert systems, Bayesian beliefnetworks, fuzzy logic, and data fusion engines) can be employed inconnection with performing automatic and/or inferred action inconnection with the disclosed subject matter.

In addition, the disclosed subject matter may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, computer-readable carrier, orcomputer-readable media. For example, computer-readable media caninclude, but are not limited to, magnetic storage devices, e.g., harddisk; floppy disk; magnetic strip(s); optical disk (e.g., compact disk(CD), digital video disc (DVD), Blu-ray Disc™ (BD); smart card(s), flashmemory device(s) (e.g., card, stick, key drive).

Moreover, terms like “user equipment” (UE), “mobile station,” “mobilesubscriber station,” “access terminal,” “terminal,” “handset,”“appliance,” “machine”, and similar terminology refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive and/or convey data associated with voice, video,sound, and/or substantially any data-stream or signaling-stream.Further, the foregoing terms are utilized interchangeably in the subjectspecification and related drawings. Likewise, the terms “local wirelesscommunications cite,” “access point” (AP), “base station,” “Node B,”“evolved Node B,” “home Node B” (HNB), “home access point” (HAP), andthe like are utilized interchangeably in the subject specification anddrawings and refer to a wireless network component or apparatus thatsends and/or receives data associated with voice, video, sound, and/orsubstantially any data-stream or signaling-stream between a set ofsubscriber stations—unless context warrants particular distinction(s)among the terms. Further, the data and signaling streams can bepacketized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“agent,”, “owner,” and the like are employed interchangeably throughoutthe subject specification and related drawings, unless context warrantsparticular distinction(s) among the terms. It should be appreciated thatsuch terms can refer to human entities, or automated componentssupported through artificial intelligence, e.g., a capacity to makeinference based on complex mathematical formalisms, that can providesimulated vision, sound recognition, decision making, etc. Also, theterms “local wireless communications cite,” “access point,” “basestation,” and the like are utilized interchangeably throughout thesubject specification, and refer to devices that can receive andtransmit signal(s) from and to wireless devices through one or moreantennas. In addition, the terms “wireless network” and “network” areused interchangeable in the subject application, unless context warrantsparticular distinction(s) among the terms.

The subject disclosure relates to methods and apparatus that effectivelymanage capacity of a wireless-based communication infrastructure.Conventional techniques that account for increased bandwidth of anasynchronous transfer mode (ATM) interface between a wireless basestation and components of an associated core network can be inefficientand prone to error. Compared to conventional techniques, various methodsand apparatus described herein efficiently configure an ATM interfacebetween a base station and radio network controller (RNC) to utilizeincreased physical capacity of the ATM interface.

Aspects, features, or advantages of the disclosed subject matter can beexploited in substantially any wireless telecommunication or radiotechnology, e.g., wireless fidelity (Wi-Fi), Worldwide Interoperabilityfor Microwave Access (WiMAX); Enhanced General Packet Radio Service(Enhanced GPRS); 3GPP Long Term Evolution (LTE); Third GenerationPartnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB); 3GPP UMTS;High Speed Packet Access (HSPA); High Speed Downlink Packet Access(HSDPA); High Speed Uplink Packet Access (HSUPA), LTE Advanced, etc.

Additionally, substantially all aspects of the disclosed subject mattercan include legacy telecommunication technologies, e.g., plain oldtelephone service (POTS). It should be appreciated that selections ofradio technology include second generation (2G), third generation (3G),and fourth generation (4G) evolution of the radio technology; however,such selections are not intended as a limitation of the disclosedsubject matter and related aspects thereof. In addition, the aspects,features, or advantages of the disclosed subject matter can be exploitedin disparate electromagnetic frequency bands.

In one non-limiting aspect, methods and apparatus are provided formanaging capacity in an asynchronous transfer mode interface within awireless network. The wireless network includes a local wirelesscommunications cite (or base station), which can use a licensed radiospectrum operated and controlled by a wireless service provider. Userequipment (UE) operated by a subscriber within a coverage area typicallycommunicates with a core network via the base station. The UE canregister with the base station and communication, e.g., voice traffic,data traffic, can be routed to the subscriber through the base stationutilizing the licensed radio spectrum. The base station can employ abackhaul network, e.g., broadband wired or wireless network backbone, toroute packet communication, e.g., voice traffic, data traffic, data, tothe core network.

FIG. 1 illustrates a wireless environment 100 that includes macro cells105 and base stations 110 for wireless coverage, in accordance with anembodiment. Each macro cell 105 represents a “macro” cell coverage area,and is served by base station 110. It should be appreciated that macrocells 105 are illustrated as hexagons; however, macro cells 105 canadopt other geometries generally dictated by a deployment or floor planof the macro cell coverage area, or covered geographic area, e.g.,metropolitan statistical area (MSA), rural statistical area (RSA), etc.Macro cell coverage is generally intended to serve mobile wirelessdevices, e.g., UE 120 _(A), UE 120 _(B), in outdoor locations. Anover-the-air wireless link 115 provides the macro coverage, and wirelesslink 115 comprises a downlink (DL) and an uplink (UL) (both not shown)that can utilize a predetermined band of radio frequency (RF) spectrumassociated with a Third Generation Partnership Project (3GPP) UniversalMobile Telecommunication System (UMTS), for example. Accordingly, UE 120_(A) can be a 3GPP UMTS mobile phone, while 120 _(E) can be a remotecomputing device with 3GPP UMTS capabilities.

Base station 110—including associated electronics, circuitry and/orcomponents—and wireless link 115 form a radio access network (RAN). Inaddition, base station 110 communicates with macro network platform 108via backhaul link(s) 151. Macro network platform 108 represents a corenetwork comprising one or more cellular wireless technologies, e.g.,3GPP UMTS, Global System for Mobile Communication (GSM). In one aspect,macro network platform 108 controls a set of base stations 110 thatserve either respective cells or a number of sectors within such cells.Macro network platform 108 can also communicate with other base stations(not shown) that serve other cells (not shown). Backhaul link(s) 151 caninclude a wired backbone link, e.g., optical fiber backbone,twisted-pair line, T1/E1 phone line, synchronous or asynchronous digitalsubscriber line (DSL), asymmetric DSL (ADSL), coaxial cable, etc.Moreover, backhaul links(s) 151 can link disparate base stations 110based on macro network platform 108.

Packet communication, e.g., voice traffic, data traffic, is typicallypaged/routed through a broadband wired network backbone (or backhaulnetwork) utilizing, e.g., optical fiber backbone, twisted-pair line,T1/E1 phone line, synchronous or asynchronous digital subscriber line(DSL), asymmetric DSL (ADSL), coaxial cable, etc. To this end, basestation 110 is typically connected to the backhaul network, e.g.,service provider network 155, via a broadband modem (not shown) andbackhaul link(s) 151. Through backhaul link(s) 151, base station 110 canhandle substantially any quality of service (QoS) for heterogeneouspacketized traffic, e.g., various multiple packet flows.

Base station 110 can integrate into an existing network, e.g., 3GPP CoreNetwork, via various interfaces, for example: via an Iub interface (notshown) between a radio network controller (RNC) 130 and base station110; via an interface (not shown) between RNC 130 and a Circuit SwitchedCore Network (CS-CN); via an interface (not shown) between RNC 130 andan Iu-CS interface; via an interface (not shown) between RNC 130 and aPacket Switched Core Network (or Iu-PS interface); via an interface (notshown) between a Serving General Packet Radio Service Support Node(SGSN) and a public data network (PDN) (or Gi interface); via aninterface (not shown) between SGSN and other SGSNs (or Gn interface).

Asynchronous Transfer Mode (ATM) can be used for 3GPP Core Network datatransmissions via the Iub interface between RNC 130 and base station110. ATM is a packet switching protocol that encodes data intofixed-size cells, and differs from other packet-switched networktechnology that uses variable sized packets, e.g., Internet Protocol(IP) or Ethernet. By utilizing a connection-oriented model, ATMestablishes a virtual circuit (or connection) between endpoints beforeexchanging data between the endpoints. Each endpoint should beconfigured via RNC 130 to support: a type of service between theendpoints; traffic parameters of data flow between the endpoints; andQoS parameters of the data flow. ATM supports different types ofservices, e.g., voice, video, data, on a network via ATM AdaptationLayers (AAL), e.g., AAL2 can be used for variable bit rate (VBR)services (e.g., voice traffic), AAL5 can be used for data transfer. AnAAL can be negotiated or configured at endpoints on aper-virtual-connection basis via RNC 130. A traffic descriptor can beused to describe service(s) or traffic characteristic(s) of a virtualcircuit established between the endpoints.

A virtual path is a bundle of virtual circuits that have the sameendpoints. The virtual path identifies a particular physical port, orphysical transmission link, which includes, for example, T1 or E1 cableconnected between two endpoints (or nodes). The physical port can forman Iub interface related to an ATM packet switching protocol. The line(or data) rate of each T1 cable included in the physical port can beapproximately 1.544 Mbits/second, while the line rate of an E1 linkincluded in the physical port can be approximately 2.048 Mbits/second. Avirtual circuit identifies a sub-bandwidth in the physical port;available physical bandwidth on a particular virtual path can bepartitioned among several virtual circuits.

Inverse Multiplexing for ATM (IMA) can be used to increase availablebandwidth of a virtual path by grouping or bundling T1 or E1 cablestogether to form an IMA Group—the resulting line rate of the virtualpath approximately a multiple of the line rate of a T1 and/or E1 cable.Accordingly, the methods and apparatus of the subject disclosure cancreate consistency, reduce errors, and effectively update an ATMinterface coupled to a base station by intelligently configuring thebase station and associated components when physical transmissionlink(s) are added to the ATM interface.

FIG. 2 illustrates a demonstrative system 200 for effectively managingcapacity of a wireless-based communication infrastructure, in accordancewith an embodiment. System 200 and the systems described below cancomprise one or more base stations 110 coupled to RNC 130 to form a UMTSTerrestrial Radio Access Network (UTRAN) 220. UTRAN 220 can be coupledto a core network, e.g., service provider network 155, via one or morebackhaul links 151 (see above) to facilitate wireless communication anddata transfer to one or more wireless devices, e.g., UE 120 _(A), UE 120_(B), in accordance with the disclosed subject matter. At least one basestation 110 can connect to RNC 130 via an Iub interface, e.g., Iubinterface 225, which can comprises an ATM packet switching protocol.

System 200 and the systems and processes explained below may constitutemachine-executable instructions embodied within a machine, e.g.,computer, readable medium, which when executed by a machine will causethe machine to perform the operations described. Additionally, thesystems and processes may be embodied within hardware, such as anapplication specific integrated circuit (ASIC) or the like. The order inwhich some or all of the process blocks appear in each process shouldnot be deemed limiting. Rather, it should be understood by a person ofordinary skill in the art having the benefit of the instant disclosurethat some of the process blocks may be executed in a variety of ordersnot illustrated.

As illustrated by FIG. 2, system 200 includes capacity managementcomponent 210. Capacity management component 210 can automateconfiguration of base station 110 and RNC 130 when physical transmissionlink(s) are added to an interface between a radio network controller anda base station, e.g., Iub interface 225. Conventional technology canaccount for physical changes in an Iub interface by way of manual,tedious, operator interface with disparate UTRAN and/or base stationconfigurations. For example, cellular cite operators/technicians shouldpossess intimate knowledge about a configuration of a particular basestation to affect use of additional T1 lines coupled to the cellularsite, e.g., by manually modifying/debugging scripts associated withprogramming components of the cellular site and/or associatedcomponents. Unlike conventional systems, capacity management component210 can reduce errors caused by manual configuration of UTRAN elementsby effectively configuring the UTRAN elements to account for additionalcapacity in associated Iub interface(s).

It should be appreciated that capacity management component 210 can belocated/included within any component, e.g., hardware, software, etc.,of UTRAN 220, e.g., base station 110, RNC 130. Also, it should beappreciated that capacity management component 210 can belocated/included within any component of a UMTS core network, e.g.service provider network 155. For example, capacity management component210 can be located/included within any component of a 3GPP network.Moreover, it should be appreciated that features and advantages of thesubject innovation can be implemented in microcells, picocells,femtocells, or the like, wherein base station 110 can be embodied in anaccess point.

FIG. 3 illustrates a capacity management component 300 for effectivelymanaging capacity of a wireless-based communication infrastructure, inaccordance with an embodiment. Capacity management component 300includes an evaluation component 310, an RNC component 320, and a basestation component 330. Evaluation component 310 can generateconfiguration data associated with a base station, e.g., base station110, of a cellular wireless network, e.g., system 200. For example, theconfiguration data can include hardware specific information associatedwith ATM line cards coupled to T1 cable and/or E1 links of a physicaltransmission link connected to the base station. RNC component 320 candetermine capacity, e.g., bandwidth, of the physical transmission link(or physical port) that forms an Iub interface of an ATM packetswitching protocol. The capacity of the physical port can be determinedby aggregating a data (or line) rate of each T1 cable (or E1 link)included in the physical port. For example, the resulting bandwidth canbe a multiple of a T1 line rate of approximately 1.544 Mbits/second, ora multiple of an E1 link line rate of approximately 2.048 Mbits/second.

The RNC component 320 can further configure an RNC coupled to the Iubinterface to utilize unused T1 and/or E1 bandwidth based on thedetermined capacity of the physical port. For example, RNC component 320can confirm whether T1 cable and/or E1 links were added to a physicaltransmission link, e.g., to increase capacity of an associated physicalport. If T1 cable and/or E1 links of the Iub interface are unused, RNCcomponent 320 can configure the RNC to utilize the increased capacityvia the ATM packet switching protocol. In addition, base stationcomponent 330 can configure the base station to utilize the increasedcapacity of the physical port based on the configuration data generatedby evaluation component 310. For example, base station component canprogram ATM line cards to utilize unused T1 cable and/or E1 linkscoupled to the ATM line cards.

Now referring to FIG. 4, an evaluation component 400 is illustrated, inaccordance with an embodiment. Evaluation component 400 can generateconfiguration data associated with a base station by utilizing a scriptcomponent 410 and polling component 420. Script component 410 can createone or more scripts based on received data, e.g., data associated withone or more base stations of a UTRAN, e.g., UTRAN 220. Each scriptcomprises a programming language that can control one or more softwareapplications. Such applications can be used to obtain information aboutvarious components of the UTRAN, and/or control various devices locatedwithin the UTRAN to affect ATM packet switching functions.

For example, script component 410 can receive a data table that at leastmaps, for at least one RNC of the UTRAN, an associated Iub name, basestation identification number, and ATM-based physical port number.Script component 410 can use this mapping information to create uniquescripts for at least one RNC. Evaluation component 400 can subsequentlyexecute the script(s) to gather data, e.g., concerning availablebandwidth of at least one Iub of a UTRAN. To this end, polling component420 can poll data associated with at least one base station of the UTRANbased on the created scripts tailored for the at least one base station.The polled data can describe current bandwidth of an Iub interfacecoupled to the base station, and information concerning virtual path(s)and circuit(s) associated with the Iub interface. Further, pollingcomponent 420 can generate configuration data of the at least one basestation of the UTRAN based on the polled data.

FIG. 5 illustrates another evaluation component 500, in accordance withan embodiment. Evaluation component 500 includes a notice component 510that can identify whether capacity of the physical port was modifiedwithin a predetermined period of time. For example, notice component 510can identify in the configuration data, e.g., via marking(s) and/orhighlight(s), that additional T1 cable and/or E1 links were added to aphysical port associated with a base station. The predetermined periodof time can be, for example, a calendar date, or a period between twodays.

Further, notice component 510 can identify whether the base station wasconfigured within the predetermined period of time. For example, noticecomponent 510 can identify in the configuration data whether hardwareand/or software affecting one or more ATM line cards at the base stationwas added and/or modified to account for additional T1 cable and/or E1links. Accordingly, in one embodiment, radio network component 700(discussed below) can configure a radio network controller to utilize anincrease in capacity of the physical port when notice component 510determines that an associated base station was not configured within apredetermined period of time after the physical port was modified.Moreover, in another embodiment, base station component 1200 canconfigure the base station based on, at least in part, the identifiedconfiguration.

FIG. 6 illustrates yet another evaluation component 600, in accordancewith an embodiment. Evaluation component 600 includes a databasecomponent 610 that can store configuration data—generated by pollingcomponent 420—in a data store (not shown). The data store can compriseany removable/non-removable storage medium. Base station component 330can configure at least one base station of a UTRAN to utilize unused T1and/or E1 bandwidth, e.g., of a physical port coupled to the basestation, based on the stored configuration data. For example, basestation component 330 can use the stored configuration data to programATM line cards located at the base station.

Now referring to FIG. 7, a radio network controller (RNC) component 700is illustrated, in accordance with an embodiment. RNC component 700includes a descriptor component 710 that can build one or moredescriptors to define traffic characteristics of a virtual path, e.g.,in order to account for an increase in capacity of an associatedphysical port. The virtual path can include one or more virtual circuitsaccording to the ATM packet switching protocol. Available bandwidth ofthe virtual path can be partitioned among the one or more virtualcircuits based on a number of T1 cable and/or E1 links connected betweenendpoints of the physical port.

In one aspect, RNC component 700 can confirm whether T1 cable and/or E1links were added to a physical port (or transmission link) associatedwith an RNC, and/or whether T1 cable and/or E1 links of the physicalport are unused. Upon confirmation of additional and/or unused capacity,RNC component 700 can configure the RNC to utilize the additional and/orunused capacity by building one or more descriptors. In one aspect,descriptor component 710 can build at least one of a traffic descriptor,a class of service descriptor, or a virtual path descriptor. A trafficdescriptor can be used to describe service(s) or trafficcharacteristic(s) of a virtual circuit established between associatedendpoints. A class of service descriptor can be used to describe QoSparameters of data flow between endpoints. A virtual path descriptor canbe used to describe characteristics of a virtual path, e.g., size of thevirtual path. For example, descriptor component 710 can build a virtualpath descriptor to account for an increase in capacity of virtualcircuits associated with the virtual path.

FIG. 8 illustrates another RNC component (800), in accordance with anembodiment. RNC component 800 includes a virtual circuit component 810that can create one or more virtual circuits within the virtual path. Asdescribed above, available bandwidth of a virtual path can bepartitioned among one or more virtual circuits, e.g., based on a numberof T1 cables and/or E1 links connected between endpoints of anassociated physical port. The line rate (or data rate) of each T1 cableincluded in a physical port is approximately 1.544 Mbits/second, whilethe line rate of an E1 link included in the physical transmission linkis approximately 2.048 Mbits/second. To account for additional/unused T1cables and/or E1 links of the physical port, virtual circuit component810 can create one or more virtual circuits within an ATM packetswitching protocol. As described above, descriptor component 710 canbuild a virtual path descriptor to account for virtual circuits createdby virtual circuit component 810. In addition, in an embodimentillustrated by FIG. 9, an RNC component 900 includes a correlationcomponent 910 that can associate one or more virtual circuits with atraffic descriptor created by descriptor component 710.

Now referring to FIG. 10, yet another RNC component (1000) isillustrated, in accordance with an embodiment. RNC component 1000includes an asynchronous transfer mode adaptation layer (AAL) component1010 that can create one or more AAL paths for the created one or morevirtual circuits. ATM supports different types of services, e.g., voice,video, data, via ATM adaptation layers, e.g., AAL2 can be used forvariable bit rate (VBR) services (e.g., voice traffic); AAL5 can be usedfor data transfer. An AAL can be negotiated or configured at endpointson a per-virtual-connection basis via an RNC, e.g., RNC 130. To thisend, in one embodiment, AAL component 1010 can create one or more AAL2paths for virtual circuits created by virtual circuit component 810. Forexample, AAL component 1010 can include AAL2 paths in an AAL2distribution unit to enable use of additional capacity associated withthe created AAL2 paths.

FIG. 11 illustrates an RNC component 1100 that includes an RNC scriptingcomponent 110, in accordance with an embodiment. RNC scripting component1110 can create one or more scripts that, when executed, can determinecapacity of a physical port coupled between a radio network controllerand base station. Further, RNC scripting component 1110 can create oneor more scripts that, when executed, can configure the radio networkcontroller to utilize additional and/or unused capacity of the physicalport based on the determined capacity. RNC scripting component 1110 cancreate the one or more scripts based on received data, e.g., dataassociated with one or more base stations of a UTRAN, e.g., UTRAN 220.Each script comprises a programming language that can control one ormore software applications. Such applications can be used to controlvarious devices located within the UTRAN, e.g., in order to affect ATMpacket switching functions.

For example, RNC scripting component 1110 can receive informationassociated with at least one base station of the UTRAN. Moreover, RNCscripting component 1010 can use this information to create the one ormore scripts that, when executed, can determine capacity of a physicalport coupled to the at least one base station; and can configure anassociated radio network controller to utilize additional capacityprovided by, e.g., new or unused T1 lines or E1 links. It should beappreciated that other RNC components described herein, e.g., 320, 700,800, 900, 1000, can include components similar to RNC scriptingcomponent 1110 that can create one or more scripts that, when executed,automate associated functions of the other RNC components.

FIG. 12 illustrates a base station component 1200, in accordance with anembodiment. Base station component 1200 includes a group component 1210,a link component 1220, and a site component 1230. Group component 1210can build one or more physical ports based on an unused capacity of aninterface, e.g., an Iub interface, between a base station and an RNC,e.g., the unused capacity determined by RNC component 320. Further,group component 1210 can add the one or more physical ports to aninverse multiplexing for asynchronous transfer mode (IMA) group. InverseMultiplexing for ATM (IMA) can be used to increase available bandwidthof a virtual path by grouping or bundling bandwidth associated withphysical paths, e.g., T1 or E1 cables, together to form an IMA Group.Link component 1220 can set a number of IMA links as a function of thebuilt one or more physical ports.

Site component 1230 can build one or more traffic descriptors that canbe used to define traffic characteristics of a virtual path associatedwith the increase in available bandwidth of the virtual path—the one ormore traffic descriptors can describe service(s) or trafficcharacteristic(s) of the virtual path. The virtual path can include oneor more virtual circuits according to ATM packet switching protocol.Available bandwidth of the virtual path can be partitioned among the oneor more virtual circuits based on, e.g., a number of T1 cable and/or E1links connected between endpoints of the physical port. Site component1230 can create one or more virtual circuits associated with the virtualpath, and relate the one or more virtual circuits with the one or moretraffic descriptors.

In addition, site component 1230 can create asynchronous transfer modeadaptation layer (AAL) paths for the created one or more virtualcircuits. ATM supports different types of services, e.g., voice, video,data, via ATM adaptation layers, e.g., AAL2 can be used for variable bitrate (VBR) services (e.g., voice traffic); AAL5 can be used for datatransfer. An AAL path can be negotiated or configured at endpoints on aper-virtual-connection basis via an RNC, e.g., RNC 130. Moreover, sitecomponent 1230 can build one or more class of service descriptorsassociated with the virtual path—the one or more class of servicedescriptors can describe QoS parameters of data flow between endpoints(or nodes) of the virtual path.

Now referring to FIG. 13, another demonstrative system 1300 foreffectively managing capacity of a wireless-based communicationinfrastructure is illustrated, in accordance with an embodiment. System1300 includes a verification component 1310 that can record, e.g., in adata store, generated configuration data, e.g., configuration datagenerated by evaluation component 310, before an associated base stationis configured to utilize unused capacity. Moreover, verificationcomponent 1310 can emphasize differences between the generated,pre-configuration data and configuration data used to configure the basestation to utilize the unused capacity. In this way, verificationcomponent can be used to troubleshoot issues affecting management of thewireless-based communication infrastructure.

FIGS. 14-23 illustrate methodologies in accordance with the disclosedsubject matter. For simplicity of explanation, the methodologies aredepicted and described as a series of acts. It is to be understood andappreciated that the subject innovation is not limited by the actsillustrated and/or by the order of acts. For example, acts can occur invarious orders and/or concurrently, and with other acts not presented ordescribed herein. Furthermore, not all illustrated acts may be requiredto implement the methodologies in accordance with the disclosed subjectmatter. In addition, those skilled in the art will understand andappreciate that the methodologies could alternatively be represented asa series of interrelated states via a state diagram or events.Additionally, it should be further appreciated that the methodologiesdisclosed hereinafter and throughout this specification are capable ofbeing stored on an article of manufacture to facilitate transporting andtransferring such methodologies to computers. The term article ofmanufacture, as used herein, is intended to encompass a computer programaccessible from any computer-readable device, carrier, or media.

Referring now to FIG. 14, a process 1400 for effectively managingcapacity of a wireless-based communication infrastructure, in accordancewith an embodiment. At 1410, one or more scripts can be executed withina cellular wireless network, e.g., a 3GPP UMTS. It should be appreciatedthat the one or more scripts comprise a programming language that cancontrol one or more software and/or hardware applications. Suchapplications can be used to obtain information about various componentsof, for example, a 3GPP UMTS, and/or control various devices locatedwithin the 3GPP UMTS, e.g., to affect ATM packet switching functions.

At 1420, configuration information associated with one or more basestations of the cellular wireless network can be assembled (orcollected) via the scripts executed at 1410. The configurationinformation can include, e.g., hardware specific information associatedwith ATM line cards coupled to T1 cable and/or E1 links of a physicaltransmission link connected to the one or more base stations. At 1430,available bandwidth of an interface, e.g., Iub interface, between atleast one base station and an associated radio controller, e.g., RNC130, can be calculated based on the assembled configuration information.

Configuration of the interface can be modified at 1440 to account foradditional physical bandwidth, e.g., available via unused T1 cable,through execution of one or more scripts at 1410. At 1450, theconfiguration of the base station associated with the interface can bemodified via scripts executed at 1410, based on configurationinformation assembled at 1420. In one embodiment of process 1400 (notshown), the configuration information assembled at 1420 can be stored ina data store, e.g., any removable/non-removable storage medium, via thescripts executed at 1410. Accordingly, configuration of the interfacecan be modified to account for additional physical bandwidth based onthe stored configuration information.

FIG. 15 illustrates a process 1500 for assembling configurationinformation associated with one or more base stations of a cellularwireless network, in accordance with an embodiment. At 1510, informationassociated with a cellular wireless network can be received. Script(s)for one or more base stations of the cellular wireless network can becreated at 1520 based on the information received at 1510. At 1530, thescript(s) can be executed (e.g., via computing device(s) located at theone or more base stations, via computing device(s) located within thecellular wireless network, via computing devices(s) remote from thecellular wireless network). The one or more base stations can be queriedat 1540 via execution of the script(s) at 1530. At 1550, theconfiguration information can be assembled based on the query of the oneor more base stations.

FIG. 16 illustrates another process (1600) for effectively managingcapacity of a wireless-based communication infrastructure, in accordancewith an embodiment. At 1610, characteristics of a virtual path, e.g.,associated with an Iub interface between a base station and a radionetwork controller, can be characterized (e.g., to determine availablebandwidth, to determine current configuration information) based onexecution of one or more scripts, e.g., created by process 1600. One ormore descriptors can be created at 1620, based on execution of the oneor more scripts and characteristics of the virtual path defined at 1610.

In an aspect (not shown), process 1600 can build at least one of atraffic descriptor, a class of service descriptor, or a virtual pathdescriptor, based on execution of the script(s). As described above, atraffic descriptor can be used to describe service(s) or trafficcharacteristic(s) of a virtual circuit established between associatedendpoints. A class of service descriptor can be used to describe QoSparameters of data flow between endpoints, e.g., associated with an Iubinterface. A virtual path descriptor can be used to describecharacteristics of a virtual path, e.g., size (or bandwidth) of thevirtual path. Accordingly, in another aspect (not shown), process 1600can build a virtual path descriptor to account for an increase incapacity of virtual circuits associated with the virtual path viaexecution of the one or more scripts.

As described above, a virtual path can include one or more virtualcircuits according to the ATM packet switching protocol. Availablebandwidth of the virtual path can be partitioned among the one or morevirtual circuits based on a number of physical links, e.g., T1 cableand/or E1 links, connected between endpoints of the physical port. Tothis end, one or more virtual circuits related to the virtual path canbe created, via execution of the one or more scripts, at 1630. At 1640,the created one or more virtual circuits can be associated (or linked)to a traffic descriptor via execution of the script(s). An asynchronoustransfer mode adaptation layer (AAL) path for at least one of thecreated one or more virtual circuits can be formed via execution of theone or more scripts at 1650.

Now referring to FIG. 17, a process 1700 for modifying an inversemultiplexing for asynchronous transfer mode (IMA) group is illustrated,in accordance with an embodiment. At 1710, one or more physical portscan be built, via execution of at least one script, based on an unusedcapacity of an interface, e.g., Iub interface, between a base stationand an RNC, e.g., an unused capacity that can be determined by RNCcomponent 320. The one or more physical ports can be included in an IMAgroup at 1720 via execution of the script(s). As described above, IMAcan be used to increase available bandwidth of a virtual path bygrouping or bundling physical links, e.g., T1 or E1 cables, together toform an IMA Group. Accordingly, a number of IMA links can be set as afunction of the number of built one or more physical ports via executionof the script(s).

FIG. 18 illustrates a process 1800 for configuring a base station, inaccordance with an embodiment. At 1810, traffic descriptor(s) can becreated by executing at least one script. The created trafficdescriptor(s) can define traffic characteristics of a virtual pathassociated with the base station—the virtual path can be created, forexample, by process 1600 described above. Class of service descriptor(s)associated with the virtual path can be built by executing at least onescript at 1820. At 1830, virtual circuit(s) associated with the virtualpath can be created by executing script(s). The virtual circuit(s) canbe related (or linked) with the traffic descriptor(s) by executing atleast one script at 1840. At 1850, AAL path(s) can be created for thevirtual circuit(s) by executing script(s).

FIG. 19 illustrates yet another process (1900) for effectively managingcapacity of a wireless-based communication infrastructure, in accordancewith an embodiment. At 1910, an increase in capacity of an interface,e.g., Iub interface, between a radio network controller and a basestation within a Universal Mobile Telecommunication System can berecognized. Descriptor(s) that define characteristics of a virtual pathassociated with the recognized increase in capacity can be built at1920. At 1930, at least one virtual circuit associated with the virtualpath can be built. The virtual circuit(s) can be correlated with thedescriptor(s) at 1940. At 1950, AAL paths can be created for the atleast one virtual circuit.

Now referring to FIG. 20, a process 2000 for configuring at least onebase station and a radio network controller in a Universal MobileTelecommunication System is illustrated, in accordance with anembodiment. At 2010, an increase in capacity (or available bandwidth) ofan interface, e.g., Iub interface, between the at least one base stationand the radio network controller can be identified. One or more physicalports associated with the interface can be created at 2020 based on theidentified increase in capacity of the interface. At 2030, one or moreof the created physical ports can be assigned to an inverse multiplexingfor asynchronous transfer mode (IMA) group. The number of IMA links canbe determined at 2040 based on the created port(s). At 2050, at leastone descriptor associated with a virtual path can be built based on theidentified increase in capacity. At least one virtual circuit associatedwith the virtual path can be built at 2060 based on the identifiedincrease in capacity. At 2070, virtual circuit(s) can be associated withthe at least one descriptor. One or more asynchronous transfer modeadaptation layer paths can be defined for the at least one virtualcircuit at 2080.

FIG. 21 illustrates a process 2100 for automatically creatingconfiguration information, in accordance with an embodiment. At 2110, adata sheet, e.g., a table, which matches one or more radio networkcontrollers to one or more base stations of a UTRAN can be received. Itcan be determined at 2120 whether the one or more base stations havebeen polled for configuration information. If it was determined that abase station has not been polled, the base station can be polled at2130; else flow can continue to 2140. In one aspect, the base stationcan be polled by recording and/or gathering data associated with theconfiguration of the base station. Such data can include, for example, anumber of T1 and/or E1 connections established at an Iub interfaceassociated with the base station. Flow can continue to 2120 after thebase station was polled at 2130.

FIG. 22 illustrates a process for automatically determining whether aphysical interface includes unused bandwidth, in accordance with anembodiment. At 2210, it can be determined whether capacity of a physicalport associated with the physical interface was modified within apredetermined period of time. The predetermined period of time can be,for example, a calendar date, or a period between two days. If it wasdetermined that capacity of the physical port was modified within thepredetermined period of time, than flow can continue to 2220, at whichit can be an identified whether a radio network controller and/or basestation associated with the physical interface were configured withinthe predetermined period of time; else flow can proceed to 2240.

If it was determined that the radio network controller and/or basestation were not configured, then flow can continue to 2230, at whichthe configuration data can be marked and/or highlighted to indicate thathardware and/or software associated with the physical port should beconfigured to account for modified capacity of the physical port, e.g.,capacity associated with unused bandwidth; else flow can proceed to2240. Flow can continue from 2230 to 2240 after configuration data ismarked and/or highlighted.

FIG. 23 illustrates a process for automatically configuring a cellularwireless network to utilize unused bandwidth, in accordance with anembodiment. At 2310, it can be determined whether a radio networkcontroller should be configured based on configuration information,e.g., information obtained by process 2100 (see above). If it wasdetermined that that the radio network controller should be configured,then flow can continue to 2320, at which the radio network controllercan be configured; else flow can proceed to 2330. Flow can continue from2320 to 2330 after the radio network controller was configured at 2320.

At 2330, it can be determined whether one or more base stations coupledto the radio network controller should be configured. If it wasdetermined that the base station(s) should not be configured, then flowcan proceed to 2360; else flow can continue to 2340, at which basestation configuration data can be obtained, e.g., by process 2100 (seeabove). Flow can continue from 2340 to 2350, at which the basestation(s) can be configured based on configuration information, e.g.,information obtained by process 2100 (see above). Flow can continue from2350 to 2360 after the base station(s) are configured.

To provide further context for various aspects of the disclosed subjectmatter, FIGS. 24 and 25 illustrate, respectively, a block diagram of anembodiment 2400 of a base station 2405 that can enable or exploitfeatures or aspects of the disclosed subject matter; and a wirelessnetwork environment 2500 that includes a macro network platform 2510,UTRAN 2590, and capacity management component 210 that exploit aspectsof the subject innovation in accordance with various aspects of thesubject specification. In embodiment 2400, base station 2405 can receiveand transmit signal(s) from and to wireless devices, e.g., wirelessports and routers, or the like, through a set of antennas 2420 ₁-2420_(N) (N is a positive integer). Antennas 2420 ₁-2420 _(N) are a part ofcommunication platform 2415, which comprises electronic components andassociated circuitry that provides for processing and manipulation ofreceived signal(s) and signal(s) to be transmitted.

In an aspect, communication platform 2415 includes areceiver/transmitter 2416 that can convert analog signals to digitalsignals upon reception of the analog signals, and convert digitalsignals to analog signals upon transmission. In addition,receiver/transmitter 2416 can divide a single data stream into multiple,parallel data streams, or perform the reciprocal operation. Coupled toreceiver/transmitter 2416 is a multiplexer/demultiplexer 2417 thatfacilitates manipulation of signal in time and frequency space.Electronic component 2417 can multiplex information (data/traffic andcontrol/signaling) according to various multiplexing schemes such astime division multiplexing (TDM), frequency division multiplexing (FDM),orthogonal frequency division multiplexing (OFDM), code divisionmultiplexing (CDM), space division multiplexing (SDM). In addition,mux/demux component 2417 can scramble and spread information (e.g.,codes) according to substantially any code known in the art, e.g.,Hadamard-Walsh codes, Baker codes, Kasami codes, polyphase codes, etc. Amodulator/demodulator 2418 is also a part of communication platform2415, and can modulate information according to multiple modulationtechniques, such as frequency modulation, amplitude modulation, e.g.,M-ary quadrature amplitude modulation (QAM), with M a positive integer),phase-shift keying (PSK), etc.

Base station 2405 also includes a processor 2435 configured to confer,at least in part, functionality to substantially any electroniccomponent in base station 2405. In particular, processor 2435 canfacilitate configuration of base station 2405 via capacity managementcomponent 210, and one or more component therein. Additionally, basestation 2405 includes display interface 2412, which can displayfunctions that control functionality of base station 2405, or revealoperation conditions thereof. In addition, display interface 2412 caninclude a screen to convey information to an end user. In an aspect,display interface 2412 can be a liquid crystal display (LCD), a plasmapanel, a monolithic thin-film based electrochromic display, and so on.Moreover, display interface can also include a component (e.g., speaker)that facilitates communication of aural indicia, which can also beemployed in connection with messages that convey operationalinstructions to an end user. Display interface 2412 also facilitatesdata entry e.g., through a linked keypad or via touch gestures, whichcan cause base station 2405 to receive external commands, e.g., restartoperation.

Broadband network interface 2414 facilitates connection of base station2405 to service provider network 155 via backhaul link(s) 151 (not shownin FIG. 24), which enables incoming and outgoing data flow. Broadbandnetwork interface 2414 can be internal or external to base station 2405,and it can utilize display interface 2412 for end-user interaction andstatus information delivery.

Processor 2435 also is functionally connected to communication platform2415 and can facilitate operations on data, e.g., symbols, bits, orchips, for multiplexing/demultiplexing, such as effecting direct andinverse fast Fourier transforms, selection of modulation rates,selection of data packet formats, inter-packet times, etc. Moreover,processor 2435 is functionally connected, via data, system, or addressbus 2411, to display interface 2412 and broadband network interface 2414to confer, at least in part, functionality to each of such components.

In base station 2405, memory 2445 can retain location and/or macrosector identifier(s); access list(s) that authorize access to wirelesscoverage through base station 2405; sector intelligence that includesranking of macro sectors in the macro wireless environment of basestation 2405, radio link quality and strength associated therewith, orthe like. Memory 2445 also can store data structures, code instructionsand program modules, system or device information, code sequences forscrambling, spreading and pilot transmission, base stationconfiguration, and so on. Processor 2435 is coupled, e.g., via a memorybus, to memory 2445 in order to store and retrieve information used tooperate and/or confer functionality to the components, platform, andinterface that reside within base station 2405.

With respect to FIG. 25, wireless communication environment 2500includes capacity management component 210 and macro network platform2510, which serves or facilitates communication with user equipment 2595via UTRAN 2590. It should be appreciated that in cellular wirelesstechnologies (e.g., 3GPP UMTS, HSPA, 3GPP LTE, 3GPP2 UMB), macro networkplatform 2510 is embodied in a core network. It is noted that UTRAN 2590can include base station(s), or access point(s), and associatedelectronic circuitry and deployment site(s), in addition to a wirelessradio link operated in accordance with the base station(s). Accordingly,UTRAN 2590 can comprise various coverage cells like cell 105. Inaddition, it should be appreciated that capacity management component210 can be included in macro network platform 3110, in UTRAN 2590, oroutside of capacity management component 210 and UTRAN 2590.

Generally, macro platform 2510 includes components, e.g., nodes,gateways, interfaces, servers, or platforms that facilitate bothpacket-switched (PS), e.g., internet protocol (IP), frame relay,asynchronous transfer mode (ATM), and circuit-switched (CS) traffic,e.g., voice and data, and control generation for networked wirelesscommunication. In an aspect of the subject innovation, macro networkplatform 2510 includes CS gateway node(s) 2512 which can interface CStraffic received from legacy networks like telephony network(s) 2540,e.g., public switched telephone network (PSTN), or public land mobilenetwork (PLMN), or a SS7 network 2560. Circuit switched gateway 2512 canauthorize and authenticate traffic, e.g., voice, arising from suchnetworks. Additionally, CS gateway 2512 can access mobility, or roaming,data generated through SS7 network 2560; for instance, mobility datastored in a VLR, which can reside in memory 2530. Moreover, CS gatewaynode(s) 2512 interfaces CS-based traffic and signaling and gatewaynode(s) 2518. As an example, in a 3GPP UMTS network, PS gateway node(s)2518 can be embodied in gateway GPRS support node(s) (GGSN).

In addition to receiving and processing CS-switched traffic andsignaling, PS gateway node(s) 2518 can authorize and authenticatePS-based data sessions with served, e.g., through macro RAN, wirelessdevices. Data sessions can include traffic exchange with networksexternal to the macro network platform 2510, like wide area network(s)(WANs) 2550; enterprise networks (NWs) 2570, e.g., enhanced 911, orservice NW(s) 2580 like IP multimedia subsystem (IMS). It should beappreciated that local area network(s) (LANs), which may be a part ofenterprise NW(s), can also be interfaced with macro network platform2510 through PS gateway node(s) 2518. Packet-switched gateway node(s)2518 generates packet data contexts when a data session is established.To that end, in an aspect, PS gateway node(s) 2518 can include a tunnelinterface, e.g., tunnel termination gateway (TTG) in 3GPP UMTSnetwork(s) (not shown), which can facilitate packetized communicationwith disparate wireless network(s), such as Wi-Fi networks. It should befurther appreciated that the packetized communication can includemultiple flows that can be generated through server(s) 2514. It is to benoted that in 3GPP UMTS network(s), PS gateway node(s) 2518 (e.g., GGSN)and tunnel interface (e.g., TTG) comprise a packet data gateway (PDG).

Macro network platform 2510 also includes serving node(s) 2516 that canconvey the various packetized flows of information, or data streams,received through PS gateway node(s) 2518. As an example, in a 3GPP UMTSnetwork, serving node(s) can be embodied in serving GPRS support node(s)(SGSN).

As indicated above, server(s) 2514 in macro network platform 2510 canexecute numerous applications, e.g., location services, online gaming,wireless banking, wireless device management, etc. that can generatemultiple disparate packetized data streams or flows; and can manage suchflows, e.g., schedule, queue, format. Such application(s), for examplecan include add-on features to standard services provided by macronetwork platform 2510. Data streams can be conveyed to PS gatewaynode(s) 2518 for authorization/authentication and initiation of a datasession, and to serving node(s) 2516 for communication thereafter.Server(s) 2514 can also effect security, e.g., implement one or morefirewalls, of macro network platform 2510 to ensure network's operationand data integrity in addition to authorization and authenticationprocedures that CS gateway node(s) 2512 and PS gateway node(s) 2518 canenact. Moreover, server(s) 2514 can provision services from externalnetwork(s), e.g., WAN 2550, or Global Positioning System (GPS)network(s), which can be a part of enterprise NW(s) 2580. It is to benoted that server(s) 2514 can include one or more processors configuredto confer at least in part the functionality of macro network platform2510. To that end, the one or more processors can execute codeinstructions stored in memory 2530, for example.

In example wireless environment 2500, memory 2530 stores informationrelated to operation of macro network platform 2510. Information caninclude business data associated with subscribers; market plans andstrategies, e.g., promotional campaigns, business partnerships;operational data for mobile devices served through macro networkplatform; service and privacy policies; end-user service logs for lawenforcement; and so forth. Memory 2530 can also store information fromat least one of telephony network(s) 2540, WAN 2550, SS7 network 2560,enterprise NW(s) 2570, or service NW(s) 2580.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “data store,” datastorage,” “database,” and substantially any other information storagecomponent relevant to operation and functionality of a component, referto “memory components,” or entities embodied in a “memory,” orcomponents comprising the memory. It will be appreciated that the memorycomponents described herein can be either volatile memory or nonvolatilememory, or can include both volatile and nonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

In order to provide a context for the various aspects of the disclosedsubject matter, FIGS. 26 and 27, as well as the following discussion,are intended to provide a brief, general description of a suitableenvironment in which the various aspects of the disclosed subject mattermay be implemented. While the subject matter has been described above inthe general context of computer-executable instructions of a computerprogram that runs on a computer and/or computers, those skilled in theart will recognize that the subject innovation also may be implementedin combination with other program modules. Generally, program modulesinclude routines, programs, components, data structures, etc. thatperform particular tasks and/or implement particular abstract datatypes.

Moreover, those skilled in the art will appreciate that the inventivesystems may be practiced with other computer system configurations,including single-processor or multiprocessor computer systems,mini-computing devices, mainframe computers, as well as personalcomputers, hand-held computing devices (e.g., PDA, phone, watch),microprocessor-based or programmable consumer or industrial electronics,and the like. The illustrated aspects may also be practiced indistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network;however, some if not all aspects of the subject disclosure can bepracticed on stand-alone computers. In a distributed computingenvironment, program modules may be located in both local and remotememory storage devices.

With reference to FIG. 26, a block diagram of a computer 2600 operableto execute the disclosed systems and methods, in accordance with anembodiment, includes a computer 2612. The computer 2612 includes aprocessing unit 2614, a system memory 2616, and a system bus 2618. Thesystem bus 2618 couples system components including, but not limited to,the system memory 2616 to the processing unit 2614. The processing unit2614 can be any of various available processors. Dual microprocessorsand other multiprocessor architectures also can be employed as theprocessing unit 2614.

The system bus 2618 can be any of several types of bus structure(s)including the memory bus or memory controller, a peripheral bus orexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MSA), Extended ISA(EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB),Peripheral Component Interconnect (PCI), Card Bus, Universal Serial Bus(USB), Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1194), and SmallComputer Systems Interface (SCSI).

The system memory 2616 includes volatile memory 2620 and nonvolatilememory 2622. The basic input/output system (BIOS), containing the basicroutines to transfer information between elements within the computer2612, such as during start-up, is stored in nonvolatile memory 2622. Byway of illustration, and not limitation, nonvolatile memory 2622 caninclude ROM, PROM, EPROM, EEPROM, or flash memory. Volatile memory 2620includes RAM, which acts as external cache memory. By way ofillustration and not limitation, RAM is available in many forms such asSRAM, dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM),Rambus direct RAM (RDRAM), direct Rambus dynamic RAM (DRDRAM), andRambus dynamic RAM (RDRAM).

Computer 2612 also includes removable/non-removable,volatile/non-volatile computer storage media. FIG. 26 illustrates, forexample, disk storage 2624. Disk storage 2624 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, Jaz drive, Zip drive, LS-100 drive, flash memory card, or memorystick. In addition, disk storage 2624 can include storage mediaseparately or in combination with other storage media including, but notlimited to, an optical disk drive such as a compact disk ROM device(CD-ROM), CD recordable drive (CD-R Drive), CD rewritable drive (CD-RWDrive) or a digital versatile disk ROM drive (DVD-ROM). To facilitateconnection of the disk storage devices 2624 to the system bus 2618, aremovable or non-removable interface is typically used, such asinterface 2626.

It is to be appreciated that FIG. 26 describes software that acts as anintermediary between users and the basic computer resources described inthe suitable operating environment 2600. Such software includes anoperating system 2628. Operating system 2628, which can be stored ondisk storage 2624, acts to control and allocate resources of thecomputer system 2612. System applications 2630 take advantage of themanagement of resources by operating system 2628 through program modules2632 and program data 2634 stored either in system memory 2616 or ondisk storage 2624. It is to be appreciated that the disclosed subjectmatter can be implemented with various operating systems or combinationsof operating systems.

A user enters commands or information into the computer 2611 throughinput device(s) 2636. Input devices 2636 include, but are not limitedto, a pointing device such as a mouse, trackball, stylus, touch pad,keyboard, microphone, joystick, game pad, satellite dish, scanner, TVtuner card, digital camera, digital video camera, web camera, and thelike. These and other input devices connect to the processing unit 2614through the system bus 2618 via interface port(s) 2638. Interfaceport(s) 2638 include, for example, a serial port, a parallel port, agame port, and a universal serial bus (USB). Output device(s) 2640 usesome of the same type of ports as input device(s) 2636.

Thus, for example, a USB port may be used to provide input to computer2612, and to output information from computer 2612 to an output device2640. Output adapter 2642 is provided to illustrate that there are someoutput devices 2640 like monitors, speakers, and printers, among otheroutput devices 2640, which use special adapters. The output adapters2642 include, by way of illustration and not limitation, video and soundcards that provide a means of connection between the output device 2640and the system bus 2618. It should be noted that other devices and/orsystems of devices provide both input and output capabilities such asremote computer(s) 2644.

Computer 2612 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)2644. The remote computer(s) 2644 can be a personal computer, a server,a router, a network PC, a workstation, a microprocessor based appliance,a peer device or other common network node and the like, and typicallyincludes many or all of the elements described relative to computer2612.

For purposes of brevity, only a memory storage device 2646 isillustrated with remote computer(s) 2644. Remote computer(s) 2644 islogically connected to computer 2612 through a network interface 2648and then physically connected via communication connection 2650. Networkinterface 2648 encompasses wire and/or wireless communication networkssuch as local-area networks (LAN) and wide-area networks (WAN). LANtechnologies include Fiber Distributed Data Interface (FDDI), CopperDistributed Data Interface (CDDI), Ethernet, Token Ring and the like.WAN technologies include, but are not limited to, point-to-point links,circuit switching networks like Integrated Services Digital Networks(ISDN) and variations thereon, packet switching networks, and DigitalSubscriber Lines (DSL).

Communication connection(s) 2650 refer(s) to the hardware/softwareemployed to connect the network interface 2648 to the bus 2618. Whilecommunication connection 2650 is shown for illustrative clarity insidecomputer 2612, it can also be external to computer 2612. Thehardware/software for connection to the network interface 2648 caninclude, for exemplary purposes only, internal and external technologiessuch as, modems including regular telephone grade modems, cable modemsand DSL modems, ISDN adapters, and Ethernet cards.

FIG. 27 illustrates a schematic block diagram of an exemplary computingenvironment 2730, in accordance with an embodiment. The system 2700includes one or more client(s) 2710. The client(s) 2710 can be hardwareand/or software (e.g., threads, processes, computing devices). Thesystem 2700 also includes one or more server(s) 2720. Thus, system 2700can correspond to a two-tier client server model or a multi-tier model(e.g., client, middle tier server, data server), amongst other models.The server(s) 2720 can also be hardware and/or software (e.g., threads,processes, computing devices). The servers 2720 can house threads toperform transformations by employing the subject innovation, forexample. One possible communication between a client 2710 and a server2720 may be in the form of a data packet transmitted between two or morecomputer processes.

The system 2700 includes a communication framework 2730 that can beemployed to facilitate communications between the client(s) 2710 and theserver(s) 2720. The client(s) 2710 are operatively connected to one ormore client data store(s) 2740 that can be employed to store informationlocal to the client(s) 2710. Similarly, the server(s) 2720 areoperatively connected to one or more server data store(s) 2750 that canbe employed to store information local to the servers 2720.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments of, and examples for, theinvention are described herein for illustrative purposes, variousmodifications are possible within the scope of the invention, as thoseskilled in the relevant art should recognize.

These modifications can be made to the invention in light of the abovedetailed description. The terms used in the following claims should notbe construed to limit the invention to the specific embodimentsdisclosed in the specification. Rather, the scope of the invention is tobe determined entirely by the following claims, which are to beconstrued in accordance with established doctrines of claiminterpretation.

1. A system comprising: a memory to store computer-executableinstructions; and a processor, communicatively coupled to the memory,that facilitates execution of the computer-executable instructions toperform operations, comprising: receiving a data table that associatesan identifier of an asynchronous transfer mode port coupled between aradio network controller device and a base station device of a cellularwireless network with another identifier of the base station device;creating a script based on the data table; determining whether aphysical transmission link has been added to the asynchronous transfermode port in response to polling information of the base station deviceutilizing the script; in response to determining that the physicaltransmission link has been added to the asynchronous transfer mode port,generating configuration data associated with an asynchronous transfermode line card of the physical transmission link; and configuring, basedon the configuration data, the asynchronous transfer mode line card toutilize an increase in capacity of the asynchronous transfer mode port.2. The system of claim 1, wherein the configuring further comprises:determining whether the capacity of the asynchronous transfer mode portwas modified within a predetermined period of time.
 3. The system ofclaim 2, further comprising: determining whether the base station devicewas configured within the predetermined period of time.
 4. The system ofclaim 1, wherein the operations further comprise: generating adescriptor that defines traffic characteristics of a virtual pathassociated with the increase in the capacity of the asynchronoustransfer mode port, wherein the virtual path includes virtual circuitsassociated with endpoints.
 5. The system of claim 4, wherein theoperations further comprise: creating a virtual circuit of the virtualcircuits that represents a sub-bandwidth of a bandwidth of theasynchronous transfer mode port.
 6. The system of claim 4, wherein theoperations further comprise: creating an asynchronous transfer modeadaptation layer path for a virtual circuit of the virtual circuits. 7.The system of claim 1, wherein the operations further comprise:determining the capacity of the asynchronous transfer mode port toobtain a determined capacity; and configuring, according to thedetermined capacity, the radio network controller device to utilize theincrease in the capacity.
 8. The system of claim 1, wherein theoperations further comprise: configuring another asynchronous transfermode port based on the increase in the capacity; and including the otherasynchronous transfer mode port in an inverse multiplexing for anasynchronous transfer mode group.
 9. The system of claim 1, wherein theradio network controller device includes the memory and the processor.10. The system of claim 1, wherein the base station device includes thememory and the processor.
 11. A method, comprising: polling, by a systemincluding a processor, data associated with a base station deviceutilizing a script; in response to the polling, determining, by thesystem, that a transmission link of an asynchronous transfer mode portcoupled to a radio network controller device and a base station devicehas been physically modified; in response to the determining,identifying, by the system, an increase in capacity of the asynchronoustransfer mode port; and configuring, by the system, a device of thetransmission link of the asynchronous transfer mode port based on theincrease in the capacity.
 12. The method of claim 11, furthercomprising: generating, by the system, a descriptor that defines trafficcharacteristics of a virtual path associated with the increase in thecapacity, wherein the virtual path includes virtual circuits associatedwith endpoints.
 13. The method of claim 11, further comprising: adding,by the system, the asynchronous transfer mode port to an inversemultiplexing for asynchronous transfer mode group.
 14. The method ofclaim 13, further comprising: configuring, by the system, an inversemultiplexing for asynchronous transfer mode link associated with theinverse multiplexing for asynchronous transfer mode group.
 15. Themethod of claim 11, further comprising: modifying, by the system, aconfiguration of the base station device based on the increase in thecapacity.
 16. A tangible computer-readable storage medium comprisingcomputer-executable instructions that, in response to execution, cause acomputing system including a processor to perform operations,comprising: in response to receiving information associated with acellular wireless network, creating a script based on the information;querying a base station device utilizing the script; identifying aphysical change associated with a transmission link of an asynchronoustransfer mode port coupled between a radio network controller device andthe base station device in response to the querying of the base stationdevice; in response to the identifying of the physical change,identifying an increase in capacity of the asynchronous transfer modeport; generating, based on the increase in the capacity, data forfacilitating a configuration of an asynchronous transfer mode line cardof the transmission link; and configuring the asynchronous transfer modeline card based on the data.
 17. The tangible computer-readable storagemedium of claim 16, wherein the operations further comprise: determiningwhether the capacity of the asynchronous transfer mode port was modifiedwithin a predetermined period of time.
 18. The tangiblecomputer-readable storage medium of claim 17, wherein the operationsfurther comprise: determining whether the base station device wasconfigured according to the data within the predetermined period oftime.
 19. The tangible computer-readable storage medium of claim 16,wherein the operations further comprise: in response to the generatingthe data, creating a descriptor representing a characteristic of avirtual path including a virtual circuit, wherein the virtual circuitrepresents a portion of a bandwidth of the asynchronous transfer modeport.
 20. The tangible computer-readable storage medium of claim 19,wherein the operations further comprise: creating an asynchronoustransfer mode adaptation layer path for the virtual circuit.